Skip to content

fix: updated OpenTelemetry distro version #61

Merged
kaleko merged 1 commit intomainfrom
fix/agentcore_evaluation
Mar 19, 2026
Merged

fix: updated OpenTelemetry distro version #61
kaleko merged 1 commit intomainfrom
fix/agentcore_evaluation

Conversation

@gauharbains
Copy link

Update OpenTelemetry distro version to 0.16.0

This PR updates the aws-opentelemetry-distro version from 0.10.1 to 0.16.0.

Problem
The previous Dockerfile was pinned to version 0.10.1, which is incompatible with AgentCore evaluations and was causing errors (see image below). While the AgentCore documentation recommends using >=0.10.0, this PR pins to an exact version (==0.16.0) rather than using >= to ensure reproducible Docker builds.

Screenshot 2026-03-19 at 3 04 41 PM

Solution

Bumping aws-opentelemetry-distro==0.16.0 resolves the incompatibility and fixes the reported error.

@gauharbains gauharbains requested a review from a team March 19, 2026 19:17
@gauharbains gauharbains changed the title fix: updated opentelemtry version fix: updated OpenTelemetry distro version Mar 19, 2026
@github-actions
Copy link

Latest scan for commit: 0fbeed1 | Updated: 2026-03-19 19:21:50 UTC

Security Scan Results

Scan Metadata

  • Project: ASH
  • Scan executed: 2026-03-19T19:21:37+00:00
  • ASH version: 3.2.2

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

  • Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
  • Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
  • High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
  • Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
  • Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
  • Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

  • Time: Duration taken by each scanner to complete its analysis
  • Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

  • PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
  • FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
  • MISSING: Scanner could not run because required dependencies/tools are not installed or available
  • SKIPPED: Scanner was intentionally disabled or excluded from this scan
  • ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

  • CRITICAL: Only Critical severity findings cause scanner to fail
  • HIGH: High and Critical severity findings cause scanner to fail
  • MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
  • LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
  • ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

  • (g) = global: Set in the global_settings section of ASH configuration
  • (c) = config: Set in the individual scanner configuration section
  • (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

  • All statistics are calculated from the final aggregated SARIF report
  • Suppressed findings are counted separately and do not contribute to actionable findings
  • Scanner status is determined by comparing actionable findings to the threshold
Scanner S C H M L I Time Action Result Thresh
bandit 0 0 0 0 0 0 807ms 0 PASSED MED (g)
cdk-nag 0 0 0 0 0 0 38.0s 0 PASSED MED (g)
cfn-nag 0 0 0 0 0 0 8ms 0 PASSED MED (g)
checkov 0 0 0 0 0 0 5.4s 0 PASSED MED (g)
detect-secrets 0 0 0 0 0 0 164ms 0 PASSED MED (g)
grype 0 0 0 0 0 0 40.0s 0 PASSED MED (g)
npm-audit 0 0 0 0 0 0 219ms 0 PASSED MED (g)
opengrep 0 0 0 0 0 0 22.1s 0 PASSED MED (g)
semgrep 0 0 0 0 0 0 16.8s 0 PASSED MED (g)
syft 0 0 0 0 0 0 1.9s 0 PASSED MED (g)

@kaleko kaleko merged commit 4bb6dc7 into main Mar 19, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants